Classifying Open-Loop And Closed-Loop Payment Cards Based On Optical Character Recognition

ABSTRACT

A user captures an image of a payment card via a user computing device camera. An optical character recognition system receives the payment card image from the user computing device. The system performs optical character recognition and visual object recognition algorithms on the payment card image to extract text and visual objects from the payment card image, which are used by the system to identify a payment card type. The system may categorize the payment card as an open-loop card or a closed-loop card, or as a credit card or a non-credit card. In an example embodiment, the system allows or prohibits extracted financial account information from the payment card to be saved in the digital wallet account based on the determined payment card category. In another example embodiment, the system transmits an advisement to the user based on the determined payment card category.

RELATED APPLICATION

This patent application claims priority under 35 U.S.C. §119 to U.S.Patent Application No. 62/024,838, filed Jul. 15, 2014, and entitled“Categorizing Payment Cards Based on Optical Character Recognization ofImages of the Payment Cards.” The entire contents of theabove-identified application are hereby fully incorporated herein byreference.

TECHNICAL FIELD

The present disclosure relates generally to improving the process forcategorizing payment cards based on optical character recognition ofimages of the cards.

BACKGROUND

User computing device applications can be used to store paymentinformation associated with payment cards for use in transactions.Closed-loop payment cards, such as merchant gift cards, can only be usedfor purchases at a specific merchant, while open-loop payment cards,such as credit cards or debit cards, can be used at multiple merchants.Generally, showing financial account information for closed-loop paymentcards on user computing device applications does not present anysecurity concerns since a closed-loop payment card can only be used atone merchant. However, showing complete financial account informationassociated with open-loop payment cards on user computing deviceapplications presents a security risk to a user because many open-loopcards are associated with personal credit accounts and bank accounts ofusers. Many open-loop cards have standardized designs since they areusable at multiple merchants.

SUMMARY

In certain example aspects described herein, computer-implementedmethods to categorize payment information as open-loop or closed-loopfor saving in a digital wallet based on optical text recognition andobject recognition of captured images of payment cards is provided. Inan example embodiment, an optical character recognition (“OCR”) systemreceives a payment card image from a user computing device and performsOCR and visual object recognition algorithms on the payment card imageto extract text and visual objects from the payment card image. For eachof the extracted visual objects, the OCR system retrieves acorresponding text description and, based on the extracted text and textdescriptions of extracted visual objects, the OCR system identifies apayment card type. The OCR system categorizes the payment card as anopen-loop card or a closed-loop card. In an example embodiment, the OCRsystem allows or prohibits extracted financial account information fromthe payment card to be saved in the digital wallet account based on thedetermined payment card category. In another example embodiment, the OCRsystem transmits an advisement to the user based on the determinedpayment card category.

In certain other example aspects described herein, systems and computerprogram products to categorize payment information as open-loop orclosed-loop for saving in a digital wallet based on optical textrecognition and object recognition of captured images of payment cardsare provided.

These and other aspects, objects, features, and advantages of theexample embodiments will become apparent to those having ordinary skillin the art upon consideration of the following detailed description ofillustrated example embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram depicting a system for categorizing paymentinformation as open-loop or closed-loop for saving in a digital walletbased on optical text recognition and object recognition of capturedimages of payment cards, in accordance with certain example embodiments.

FIG. 2 is an example illustration of an open-loop payment card and aclosed-loop payment card, in accordance with certain exampleembodiments.

FIG. 3 is a block flow diagram depicting a method for saving paymentinformation categorized as open-loop or closed-loop based on a capturedimage of a payment card, in accordance with certain example embodiments.

FIG. 4 is a block flow diagram depicting a method for capturing an imageof a payment card, in accordance with certain example embodiments.

FIG. 5 is a block flow diagram depicting a method for selecting apayment card for use in a transaction, in accordance with certainexample embodiments.

FIG. 6 is a block diagram depicting a computing machine and module, inaccordance with certain example embodiments.

DETAILED DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

The example embodiments described herein provide computer-implementedtechniques for categorizing payment information as open-loop orclosed-loop for saving in a digital wallet based on optical textrecognition and object recognition of captured images of payment cards.In an example embodiment, a user captures an image of a payment card viaa user computing device camera. An optical character recognition (“OCR”)system receives the payment card image from the user computing device.The OCR system performs OCR and visual object recognition algorithms onthe payment card image to extract text and visual objects from thepayment card image. For each of the extracted visual objects, the OCRsystem retrieves a corresponding text description. Based on theextracted text and text descriptions of extracted visual objects, theOCR system identifies a payment card type. In an example embodiment, theOCR system categorizes the payment card as an open-loop card or aclosed-loop card. In an example embodiment, the OCR system allows orprohibits extracted financial account information from the payment cardto be saved in the digital wallet account based on the determinedpayment card category. In another example embodiment, the OCR systemtransmits an advisement to the user based on the determined payment cardcategory.

In an example embodiment, a user selects a digital wallet application ona user computing device. The digital wallet application on the usercomputing device is associated with a payment processing system andcommunicates with the payment processing system. In this example, theuser may register with the payment processing system to create a digitalwallet account and may download the digital wallet application onto theuser computing device. In an example embodiment, the digital walletapplication stores payment account information associated with the userfor use in transactions. The user selects an option to add a new paymentcard to the digital wallet application. An example payment cardcomprises a credit card, a debit card, a stored value card or other giftcard, a coupon, a voucher card, a rewards points card, a loyalty card,or other card appropriate for use in a transaction. In this example, atransaction may comprise a purchase, exchange, return, or redemption ofgoods or services and may comprise transfers of funds, credits, points,or any other appropriate unit of value to or from a user financialaccount associated with a corresponding payment card.

The user computing device camera module is activated. In an exampleembodiment, the digital wallet application activates a camera moduleresident on the user computing device in response to the user selectingan option to add a new payment card to the digital wallet application.In this example embodiment, the camera module communicates with the usercomputing device, which comprises a camera device. In another exampleembodiment, a camera device is separate from the user computing deviceand communicates with the user computing device over a network. Inanother example embodiment, the user activates the camera modulemanually by actuating an object on the user interface of the usercomputing device. The user captures an image of the payment card. In anexample embodiment, the user actuates an interface object on the usercomputing device to capture the image of the payment card. In thisexample embodiment, the user captures an image of the front side of thepayment card, an image of the back side of the payment card, or multipleimages of both the front side and the back side of the payment card. Forexample, the digital wallet application displays a live stream of thecamera feed to enable the user to aim the camera module or camera deviceto capture an adequate image of the payment card. In this example, theuser positions the payment card and/or the user computing device withina viewing area displayed by the user computing device and actuates anobject on the user interface to capture the image of the payment card.For example, the user touches a “take picture” interface object on atouch screen interface of the user computing device to take a picture ofthe payment card. In another example embodiment, the user capturesmultiple images of the payment card and the digital wallet applicationselects one of the multiple images.

The image or images of the payment card are transmitted by the usercomputing device to an optical character recognition (“OCR”) system. Inan example embodiment, some, or all, of the functions of the OCR systemmay be performed by an OCR system application module. In another exampleembodiment, some or all of the functions attributed to as beingperformed by the OCR system may be performed by the user computingdevice. For example, instead of transmitting the captured image of thepayment card to the OCR system, the user computing device may performcharacter and image recognition on the captured image. In an exampleembodiment, the OCR system application module, the user computing devicecamera module, the user computing device, or other computing deviceperforms blur detection on the image. For example, the image may berecognized as blurry, overly bright, overly dark, or otherwise obscuredin a manner that prevents a high resolution image from being obtained.In this example embodiment, the appropriate device may adjust the imagecapturing method to reduce the blur in the image. For example, the OCRsystem may transmit a request to the user computing device instructingthe camera module to adjust the focus on the payment card, instructingthe user to move the camera device or user computing device comprising acamera device closer to or farther away from the payment card, or anyother appropriate instruction. In this example, the user captures asubsequent image of the payment card using the user computing device orcamera device and the user computing device transmits the subsequentimage to the OCR system. In another example, the user computing device,digital wallet application residing on the user computing device, orcamera module residing on the user computing device may request that thecamera module and/or the user perform similar actions to receive asubsequent image to transmit to the OCR system.

In another example embodiment, the OCR system application module mayperform a digital image manipulation or any other suitable method toremove a blur in the image. In an example embodiment, the OCR systemapplication module isolates the image of the payment card from thereceived image using image data manipulation or image extractiontechniques. For example, the received image may comprise an image of apayment card taken on the background of a kitchen table. In thisexample, the OCR system application module isolates and extracts theimage of the payment card from the background image of the table tocreate an image comprising only the payment card. In some exampleembodiments, the OCR system application module received imagescomprising images of the front and back of the payment card. In theseexample embodiments, the OCR system application module may isolate andextract the images of the front and back sides of the payment card tocreate a combined image comprising only the payment card.

The OCR system extracts alphanumeric text from the image of the paymentcard. In an example embodiment, the OCR system application moduleapplies an OCR algorithm to the card image to identify the informationon the card. The OCR algorithm may represent any suitable process,program, method, or other manner of recognizing the digits or charactersrepresented on the card image. In an example embodiment, the OCRalgorithm may be customized to look for characters in particularlocations on the image of the payment card, to look for a certain numberof characters, or to look for certain combinations of characters. Forexample, it may be an industry standard for certain types of paymentcards to have 15 or 16 numerical digits in a certain location on thepayment card. In an example embodiment, the OCR system applicationmodule identifies each character and categorizes the groups ofcharacters. For example, the OCR system application module may determinethat a group of characters comprise a name, account number, expirationdate, and other suitable categories of data.

The OCR system extracts visual objects from the image of the paymentcard. The OCR system application module may use any suitable algorithm,process, method, or other manner of recognizing card images. Forexample, the OCR system application module may isolate visual objects,such as card art, within the image of the card and can compare thevisual object images to a stored database of images to identify matchingimages. The OCR system retrieves a text description of extracted visualobjects. For example, when the OCR system compares the identified visualobject to a database of images and locates a matching image, the OCRsystem accesses stored data associated with the matching image. The datastored with the matching images may include an identification of thepayment card type. For example, the OCR system may identify a logo onthe card image that matches a logo in the database and retrieve a textdescription from the database that identifies the logo as pertaining toa particular bank, merchant system, issuer system, acquirer system, orother appropriate system.

The OCR system identifies the payment card as either an open-looppayment card or a closed-loop payment card based on the extracted textand the retrieved text description of extracted visual objects in theimage of the payment card. For example, an open-loop payment card is apayment card that can be used in transactions with multiple merchantsystems, for example, a credit card, a debit card, or a universal giftcard issued by a credit card system. A closed-loop payment card is apayment card that can be used in transactions with one merchant systemonly or with a limited number of merchants. In certain exampleembodiments, the digital wallet application is configured to saveclosed-loop payment card information in the digital wallet application,but not to save open-loop payment card information due to user securityconcerns or open-loop display requirements.

In certain example embodiments described herein, if the OCR systemidentifies the payment card as an open-loop card, the OCR systemtransmits a notification to the digital wallet application on the usercomputing device that the payment card is an open-loop card. In theseexample embodiments, the user computing device notifies the user thatthe payment card is not savable in the digital wallet application. Forexample, the user computing device displays a message on the userinterface that says “debit/credit/universal gift cards/etc. are notsavable on this application. Please try a different card.” In theseexample embodiments, if the OCR system identifies the payment card as aclosed-loop payment card, the OCR system application module transmitspayment information associated with the payment card (for example,information captured from the image of the card) to the digital walletapplication on the user computing device. In this example, the digitalwallet application saves the closed-loop payment card information on theuser computing device.

In certain example embodiments, the digital wallet application does notsave open-loop payment cards and in other example embodiments, exclusionof open-loop payment cards is not performed. In other exampleembodiments, open-loop cards are savable to the digital walletapplication, and the OCR system does not differentiate in treatment ofthe payment card types. In these example embodiments, once paymentinformation is obtained for a payment card, the payment information istransmitted to the digital wallet application for saving on the usercomputing device by the digital wallet application. In an exampleembodiment, saving the payment card information comprises saving theimage of the payment card and any information necessary or useful toconduct a digital wallet transaction with the saved payment card. Incertain example embodiments, the OCR system identifies the merchantsystem, financial institution, issuer system, and/or acquirer systemassociated with the payment card. In certain example embodiments, theOCR system identifies a type for an open-loop card. For example, the OCRsystem identifies an open-loop card as a credit card, a debit card, auniversal gift card associated with a credit card system, or anotheropen-loop card type.

In certain example embodiments, the user initiates a digital wallettransaction. For example, the user accesses a website associated with apeer to peer transaction system using the user computing device, selectsanother user with whom to initiate a payment transfer, and selects anamount to transfer. In another example embodiment, the user initiates atransaction with a merchant system point of sale (“POS”) system at aphysical store location. In an example embodiment, the user selects anoption to pay using the digital wallet application. The digital walletapplication presents the user with a list of saved payment cards, thesaved payment cards comprising saved images of payment cards captured bythe user computing device camera module or other capture device. In anexample embodiment, the user is presented with images of each of thepayment cards in the payment card list for selection. For example, thelist of saved payment cards may comprise one or multiple debit cards,credit cards, loyalty cards, rewards cards, coupon cards, gift cards orother stored value cards, or other payment cards entered by the user,depending on the configurations of the digital wallet application.

The user selects a payment card from the digital wallet account. In anexample embodiment, the user actuates an object on the user interface ofthe user computing device to select the payment card from one or morepayment cards stored on in the user's 101 digital wallet account. Forexample, the user touches an image of the payment card on a touchscreenuser interface to select the payment card. In this example, the user mayselect an option on the digital wallet application to capture the imageof the payment card. In an example embodiment, the digital walletapplication transmits one or multiple saved or captured imagesassociated with the selected payment card to the OCR system applicationmodule for text and image recognition. In another example embodiment,the digital wallet application has previously sent an image of thepayment card to the OCR system and received payment informationassociated with the payment card image from the OCR system. Thetransaction is processed. For example, a payment processing systemassociated with the user's digital wallet account processes thetransaction by communicating with a credit card network or a financialinstitution system associated with the payment card selected by the userfor use in the transaction.

By using and relying on the methods and systems described herein, an OCRsystem may categorize payment cards as open-loop or closed-loop forsaving in a digital wallet account based optical text recognition andobject recognition of captured images of payment cards. Additionally, byreceiving a categorization of the payment cards from the OCR system, apayment processing system associated with a digital wallet account towhich a user is attempting to upload the payment cards may improve thesecurity of the user's financial information by not displaying paymentinformation or not saving payment card information associated with acertain category.

Example System Architecture

Turning now to the drawings, in which like numerals indicate like (butnot necessarily identical) elements throughout the figures, exampleembodiments are described in detail.

FIG. 1 is a block diagram depicting a system 100 for identifying paymentcards via object recognition and optical text recognition of paymentcard images, in accordance with certain example embodiments. As depictedin FIG. 1, the system 100 includes network computing systems 110 and 140that are configured to communicate with one another via one or morenetworks 120. In some embodiments, a user associated with a device mustinstall an application and/or make a feature selection to obtain thebenefits of the techniques described herein.

The network 120 can include a local area network (“LAN”), a wide areanetwork (“WAN”), an intranet, an Internet, storage area network (“SAN”),personal area network (“PAN”), a metropolitan area network (“MAN”), awireless local area network (“WLAN”), a virtual private network (“VPN”),a cellular or other mobile communication network, Bluetooth, Bluetoothlow energy, near field communication (“NFC”), Wi-Fi, or any combinationthereof or any other appropriate architecture or system that facilitatesthe communication of signals, data, and/or messages. Throughout thediscussion of example embodiments, it should be understood that theterms “data” and “information” are used interchangeably herein to referto text, images, audio, video, or any other form of information that canexist in a computer-based environment.

Each network computing device 110 and 140 includes a device having acommunication module capable of transmitting and receiving data over thenetwork 120. For example, each network computing device 110 and 140 caninclude a server, desktop computer, laptop computer, tablet computer, atelevision with one or more processors embedded therein and/or coupledthereto, smart phone, handheld computer, personal digital assistant(“PDA”), or any other wired or wireless, processor-driven device. In theexample embodiment depicted in FIG. 1, the network computing devices 110and 140 are operated by users and OCR system operators, respectively.

An example user computing device 110 comprises a user interface 111, acamera module 113, a data storage unit 115, a communication application117, and a digital wallet application 119.

In an example embodiment, the user interface 111 enables the user 101 tointeract with the digital wallet application 119. For example, the userinterface 119 may be a touch screen, a voice-based interface or anyother interface that allows the user 101 to provide input and receiveoutput from an application or module on the user computing device 110.

In an example embodiment, the camera module 113 comprises any module orfunction of the user computing device 110 that obtains a digital image.In other example embodiments, a camera device obtains or captures adigital image and transmits the image to the user computing device 110.The camera module 113 may be onboard the user computing device 110 or inany manner logically connected to the user computing device 110. Thecamera module 113 may be capable of obtaining individual images or avideo scan. Any other suitable image capturing device may be representedby the camera module 113. In an example embodiment, the camera module113 may control an associated camera device to capture an image orrecord a video of a payment card 130. In an example embodiment, thecamera module 113 communicates with the digital wallet application 119and/or the OCR system 140 to transmit the captured image of the paymentcard 130.

In an example embodiment, the data storage unit 115 comprises a local orremote data storage structure accessible to the user computing device110 suitable for storing information. In an example embodiment, the datastorage unit 115 stores encrypted information, such as HTML5 localstorage. In an example embodiment, the data storage unit 115 storesfinancial account information associated with one or more payment cards130 for use by the digital wallet application 119.

In an example embodiment, the user 101 can use a communicationapplication 113, such as a web browser 114 application or a stand-aloneshopping application 116, to view, download, upload, or otherwise accessdocuments or web pages via a distributed network 120. In an exampleembodiment, the communication application 113 can interact with webservers or other computing devices connected to the network 120,including the user computing device 110 and a web server 143 associatedwith an OCR system 140.

In an example embodiment, the digital wallet application 119 is aprogram, function, routine, applet, or similar entity that exists on andperforms its operations on the user computing device 110. In certainembodiments, the user 101 must install the digital wallet application119 and/or make a feature selection on the user computing device 110 toobtain the benefits of the techniques described herein. In an exampleembodiment, the user 101 may access the digital wallet application 119on the user computing device 110 via the user interface 111. In anexample embodiment, the digital wallet application 119 can be selectedby a user on the user computing device 110 and used to initiate a peerto peer transaction by a user. In another example embodiment, thedigital wallet application 119 may be used in an online transaction bythe user with a merchant system. In an example embodiment, the digitalwallet application 119 is associated with a payment processing system150 and communicates with the payment processing system 150. In anexample embodiment, the digital wallet application 119 communicates withan online digital wallet account managed by the payment processingmodule 151.

In certain example embodiments, one or more functions herein describedas performed by the digital wallet application 119 may also be performedby the OCR system application module 143 associated with an OCR system140. In certain example embodiments, one or more functions hereindescribed as performed by the digital wallet application 119 may also beperformed by the user computing device 110 operating system or a webbrowser application executing on the user computing device 110.

In an example embodiment, the user computing device 110 communicateswith the OCR system 140 via the network 120.

An example OCR system 140 comprises an OCR system application module 143and a data storage unit 145.

In an example embodiment, the OCR system application module 143 performsthe functions of optical character recognition (“OCR”) and visual objectrecognition for the OCR system 140. For example, OCR may compriserecognition of numbers, letters, symbols, and other characters on apayment card image and visual object recognition may comprise computerrecognition of a logo on the payment card image. Visual objectrecognition may comprise recognition of logos associated with a paymentcard image. In an example embodiment, the OCR system comprises adatabase that is used to match extracted visual objects with acorresponding text description of the visual objects and retrieve thetext descriptions. In an example embodiment, the OCR system 140categorizes the payment card 130 based on OCR and visual objectrecognition. In an example, the OCR system 140 categorizes the paymentcard 130 as an open-loop payment card 130 or a closed-loop payment card130. In another example, the OCR system 140 categorizes the payment card130 as a credit payment card 130 or a non-credit payment card 130.

In an example embodiment, the data storage unit 145 comprises a local orremote data storage structure accessible to the OCR system 140 and/orOCR system application module 143 suitable for storing information. Inan example embodiment, the data storage unit 145 stores encryptedinformation, such as HTML5 local storage. In an example embodiment, thedata storage unit 145 is resident on the OCR system application module143.

An example payment processing system 150 comprises a payment processingmodule 151 and a data storage unit 155.

In an example embodiment, the payment processing module 151 processes atransaction initiated by a user using financial account informationassociated with a digital wallet account. In an example embodiment, thepayment processing module 151 accesses financial account informationselected by the user from the digital wallet account for use in thetransaction. For example, the payment processing module 151 may receivea notification of a selection of the payment card from the usercomputing device 110 over the network 120 and may access the datastorage unit 155 to retrieve financial account information associatedwith the payment card 130 selected by the user. In an exampleembodiment, the payment processing module communicates with a creditcard processing system or a financial institution system over thenetwork 120 to process the transaction. An example credit cardprocessing system may comprise an issuer system and an acquirer systemassociated with a user credit card selected by the user for use in thetransaction. An example financial institution system comprises a bankthat is associated with a debit card selected by the user for use in thetransaction. In an example embodiment, the payment processing module 151generates a receipt and transmits the receipt to the user computingdevice 110. An example receipt may comprise a transaction summarycomprising a list of the items purchased, a total amount for thetransaction, the payment instrument used, the user's name, and/or otherrelevant or useful information associated with the transaction. Inanother example, the transaction is unsuccessful and the receiptcomprises a statement that the transaction could not be completed orthat the transaction has been canceled.

In an example embodiment, the data storage unit 155 comprises a local orremote data storage structure accessible to the payment processingsystem 150 suitable for storing information. In an example embodiment,the data storage unit 155 stores encrypted information, such as HTML5local storage. In an example embodiment, the data storage unit 155stores financial account information associated with one or more paymentcards 130 in a digital wallet account associated with a user. In anexample embodiment, the payment processing system 150 receives thefinancial account information associated with the one or more paymentcards from the OCR system 140. For example, the OCR system 140 analyzesone or more images of one or more payment cards 130 received from a usercomputing device 110 and extracts financial account information from theone or more images.

It will be appreciated that the network connections shown are exampleand other means of establishing a communications link between thecomputers and devices can be used. Additionally, those having ordinaryskill in the art having the benefit of the present disclosure willappreciate that the user computing device 110 and the OCR system 140illustrated in FIG. 1 can have any of several other suitable computersystem configurations. For example, a user computing device 110 embodiedas a mobile phone or handheld computer may or may not include all thecomponents described above.

In example embodiments, the network computing devices and any othercomputing machines associated with the technology presented herein maybe any type of computing machine such as, but not limited to, thosediscussed in more detail with respect to FIG. 6. Furthermore, anymodules associated with any of these computing machines, such as modulesdescribed herein or any other modules (scripts, web content, software,firmware, or hardware) associated with the technology presented hereinmay by any of the modules discussed in more detail with respect to FIG.6. The computing machines discussed herein may communicate with oneanother as well as other computer machines or communication systems overone or more networks, such as network 120. The network 120 may includeany type of data or communications network, including any of the networktechnology discussed with respect to FIG. 6.

Example Processes

The example methods illustrated in FIGS. 3-5 are described hereinafterwith respect to the components of the example operating environment 100.The example methods of FIGS. 3-5 may also be performed with othersystems and in other environments.

FIG. 3 is a block diagram depicting a method 300 for saving paymentinformation categorized as open-loop or closed-loop based on a capturedimage of a payment card, in accordance with certain example embodiments.The method 300 is described with reference to the components illustratedin FIG. 1.

In block 310, a user captures an image of a payment card 130 via a usercomputing device 110.

The method for capturing an image of a payment card 130 is described inmore detail hereinafter with reference to the method described in FIG.4.

FIG. 4 is a block diagram depicting a method 310 for capturing an imageof a payment card 130, in accordance with certain example embodiments.The method 410 is described with reference to the components illustratedin FIG. 1.

In block 410, the user selects the digital wallet application 119 on theuser computing device 110. In an example embodiment, the digital walletapplication 119 stores financial account information or has access tofinancial account information stored in the user computing device datastorage unit 115. In an example embodiment, the digital walletapplication 119 is associated with a payment processing system (notshown). In this example embodiment, the user establishes a digitalwallet account with the payment processing system and the paymentprocessing system communicates with the digital wallet application 119over a network 120. The user may download the digital wallet application119 onto the user computing device 110 from a website associated withthe payment processing system after establishing the digital walletaccount with the payment processing system. In the example embodiment,the user may add, delete, or edit personal information and/or financialaccount information via the digital wallet application 119, whichcommunicates with the payment processing system.

In block 420, the user selects an option to add a new payment card 130.In an example embodiment, the digital wallet application 119 presentsone or more objects on the user interface 111 of the user computingdevice 110 that enable the user to add, edit, organize, delete, orperform some other appropriate function with information in the user'sdigital wallet account. In an example embodiment, the user selects anoption to add a new payment card 130 by capturing an image of thepayment card. For example, the user actuates an object on the userinterface 111 on the user computing device 110 to select an option thatreads “add a new payment card by taking a picture.”

In block 430, the user computing device camera module 113 is activated.In an example embodiment, the digital wallet application 119communicates with the camera module 113 and/or the user computing device110 operating system to activate the camera module 113. In an exampleembodiment, the camera device that communicates with the user computingdevice 110 is activated. In this example embodiment, the user computingdevice 110 may communicate with the camera device via a network 120. Inanother example embodiment, the user activates the camera module 113 orthe camera device. In yet another example embodiment, the user does notactivate the camera module 113 at this time, but has previously capturedone or more images of a payment card 130 using the user computing device110, wherein the user computing device 110 saved the one or more imageson the data storage unit 115. In this example embodiment, the userselects the saved one or more images of the payment card 130 to add thenew payment card 130 to the digital wallet application 119.

In block 440, the user captures an image of the payment card 130. Inthis example embodiment, the user may capture an image of the front ofthe payment card 130, an image of the back of the payment card 130, orone or more images of the front and/or the back of the payment card 130.In this example embodiment, the “front” of the payment card 130 may beidentified as the side of the payment card 130 that lists the accountnumber and/or a user's name on the payment card 130. In another exampleembodiment, the user does not capture an image of the payment card 130at this time, but instead accesses a previously captured image of thepayment card 130. For example, the camera module 113, digital walletapplication 119, or user computing device 110 are used by the user toaccess one or more images of the payment card 130 saved in the datastorage unit 115 resident on the user computing device 110. In theexample embodiments described herein, a payment card 130 may comprise acredit card, a debit card, a stored value card, a gift card, a coupon, avoucher card, a rewards points card, a loyalty card, or other paymentcard 130 appropriate for use in a transaction. In this example, atransaction may comprise the purchase, exchange, return, or redemptionof goods or services and may comprise transfers of funds, credits,points, or any other appropriate unit of value to or from a userfinancial account associated with the payment card 130.

In block 450, the user computing device 110 transmits the image of thepayment card 130 to the OCR system 140. The optical characterrecognition (“OCR”) system 140 may comprise an OCR system applicationmodule 143 that is capable of recognizing text and visual objects in animage. In another example embodiment, the user computing device 110transmits two or more images of the payment card 130 to the OCR system140. In an example embodiment, the user computing device 110 transmitsone or more images of the payment card 130 over the network 120. In anexample embodiment, the user computing device 110 transmits the one ormore images of the payment card 130 to a payment processing system thatcomprises the OCR system 140. In an example embodiment, the usercomputing device 110, in addition to transmitting the one or more imagesof the payment card to the OCR system 140, also saves one or more copiesof the one or more images of the payment card 130 in the data storageunit 115 resident on the user computing device 110. In another exampleembodiment, the user computing device 110 does not transmit the paymentcard image to the OCR system 140 and actions described herein as beingperformed by the OCR system 140 or OCR system application module 143 areperformed by the digital wallet application 119 and/or the usercomputing device 110.

Returning to FIG. 3, in block 320, the OCR system 140 receives the imageof the payment card 130. In an example embodiment, the OCR system 140receives the image of the payment card 130 at the OCR system applicationmodule 143 via the network 120. In another example embodiment, the OCRsystem 140 otherwise receives the one or more images of the payment card130.

In block 330, the OCR system 140 extracts text from the image of thepayment card 130. In an example embodiment, the OCR system applicationmodule 143 extracts the text from the image of the payment card 130. Inanother example embodiment, the OCR system application module 143extracts texts from two or more images of the payment card 130. In anexample embodiment, the OCR system application module 143 applies anoptical character recognition (“OCR”) algorithm to the payment cardimage to identify the information on the payment card. The OCR algorithmmay represent any suitable process, program, method, or other manner ofrecognizing the digits or characters represented on the payment cardimage. In an example embodiment, the OCR algorithm may be customized tolook for characters in particular locations on the image of the paymentcard 130, to look for a certain number of characters, or to look forcertain combinations of characters. For example, it may be an industrystandard for certain types of payment cards 130 to comprise a 15 or 16numerical digit user account number in a certain location on the paymentcard 130, the user's name on a certain location on the payment card 130,and/or the expiration date of the payment card 130 on a certain locationon the payment card. In an example, an expiration date may be inMM/DD/YYYY, MM/DD/YY, MM/YY, or MM/YYYY format, M representing a numberassociated with a month, D representing a number associated with anumerical day, and Y representing a number associated with a year. In anexample embodiment, the OCR system application module 143 identifieseach character and categorizes the groups of characters. For example,the OCR system application module 143 may determine that a group ofcharacters comprise a name, account number, expiration date, and othersuitable categories of data.

In block 340, the OCR system 140 extracts visual objects from the imageof the payment card 130. In an example embodiment, the OCR systemapplication module 143 extracts the visual objects from the image of thepayment card 130. The OCR system application module 143 may use anysuitable algorithm, process, method, or other manner of recognizing cardimages. For example, the OCR system application module 143 may isolatevisual objects, such as card art, within the image of the payment card130 and can compare the visual object images to a stored database ofimages to identify matching images. For example, the payment card 130may comprise a logo of a merchant system, issuer system, acquirersystem, or financial institution associated the payment card 130. Inaddition to visual objects, the OCR system application module 143 mayextract features of the payment card image, such as color, brightness,pattern, lines, shapes, shading, a holographic nature of an object,and/or other appropriate or relevant features of the payment card image.

In block 350, the OCR system 140 retrieves a text description ofextracted visual objects. In an example embodiment, when the OCR system140 or OCR system application module 143 compares the identified visualobject to a database of images and locates a matching image, the OCRsystem 140 accesses stored data associated with the matching imagecomprising a text description of the visual object. In this exampleembodiment, the database of images may be resident on the data storageunit 145 of the OCR system application module 143. The data stored withthe matching images may comprise an identification of the payment card130 type. For example, the OCR system 140 may identify a logo on thepayment card image that matches a logo in the database and retrieve atext description from the database that identifies the logo aspertaining to a particular bank, merchant system, issuer system,acquirer system, or other appropriate system associated with the paymentcard 130. An example text description of a visual object or logo maycomprise the bank, merchant, issuer, or acquirer name. The textdescription may also comprise a specific type of payment card 130, suchas credit card, gift card, or debit card. In an example embodiment, theOCR system 140 may populate the database with visual object imagesassociated with a plurality of common payment card formats and createand associate text descriptions with these the visual object images. Incertain example embodiments, the database of images may directlyassociate or otherwise correlate an image with the relevant information,in which case the text transition step may not be needed.

In block 360, the OCR system 140 determines, based on the textdescription of extracted visual objects and text extracted from theimage of the payment card 130 or otherwise associated therewith, whetherthe payment card 130 is an open-loop payment card or a closed-looppayment card. In the example embodiments described herein, an open-looppayment card comprises a payment card 130 that can be used intransactions with more than one merchant system, and a closed-looppayment card 130 comprises a payment card 130 that can only be used intransactions with a specific merchant system associated with the paymentcard 130. For example, credit cards and debit cards are open-looppayment cards 130 as they can be used in transactions with multiplemerchant systems. In this example, a universal gift card is an open-looppayment card, whereas a merchant-specific gift card is a closed-looppayment card.

FIG. 2 is an example illustration of an example open-loop card 130-A andclosed-loop card 130-B, in accordance with certain example embodiments.The purpose of this illustration is to illustrate example methods ofidentifying differences between open-loop cards 130-A and closed-loopcards 130-B. Open-loop cards 130-A and/or closed-loop cards 130-B may beof a variety of formats. For example, an example open-loop card 130-Amay comprise an issuer system name or acquirer system name listed on thefront of the payment card 130, while a closed-loop card may list thename of the merchant system to which the payment card 130 is associated.Another example difference is that the positioning of a logo on anopen-loop card 130-A may be standardized in the payment card 130industry, thus facilitating an identification of a closed-loop card130-B based on nonstandard logo positioning. In yet another example, anOCR system 140 may identify an open-loop card 130-A or closed-loop card130-B based on the number of digits on an account number displayed on animage of the payment card 130. Other features of payment cards 130 (andtheir resulting captured images), such as color, shape, pattern, lines,shading, brightness, or other optically distinguishable features, mayalso be applicable in distinguishing between open-loop and closed-looppayment cards 130. In an example embodiment, the OCR system 140 extractsone or more of these features and compares the features to a database offeatures/card types to determine whether the payment card 130 is anopen-loop or closed-loop payment card 130. For example, certainfeatures, such as logos associated with merchant systems, issuersystems, or banking systems, may be associated with open-loop orclosed-loop payment cards 130. For example, a bank-issued debit paymentcard 130 is an open-loop card and not a closed-loop card. In an exampleembodiment, the bank-issued debit payment card 130 comprises a logofeature associated with the issuing bank. In this example embodiment,the OCR system 140 detects the logo associated with the issuing bank andclassifies the payment card 130 as not closed-loop based on the logo. Inan example embodiment, a merchant system is more likely to issue aclosed-loop card that is only usable with the merchant system. Forexample, the merchant system issues a gift card comprising a merchantlogo feature. In this example, the OCR system 140 detects the merchantlogo and classifies the gift card as a closed-loop gift card based onthe merchant logo.

Returning to block 360, in FIG. 3, if the OCR system 140 determines thatthe payment card 130 is a closed-loop payment card 130, the method 300proceeds to block 390. In an example embodiment, the OCR system 140determines that the payment card is a closed-loop payment card 130 basedon the identified visual objects in the payment card image, extractedtext from the visual card image, regions of color, shape, pattern,lines, shading, or brightness on the payment card 130, and/or otherappropriate features of the payment card 130 that can be opticallydetected by the OCR system 140. For example, a closed-loop payment card130 may be identified based on the presence of a merchant name on thepayment card image. In another example, a logo of a certain color,shape, and shading is detected in a certain position on the payment card130 is searched in the OCR system application module 143 database anddetermined that the payment card 130 is a merchant gift card and thus aclosed-loop payment card 130.

In block 390, the OCR system 140 saves payment card 130 information inthe digital wallet account. In an example embodiment, the OCR system 140communicates with the payment processing system associated with thedigital wallet application to save the payment card information in thedigital wallet account on the payment processing system and/or thedigital wallet application on the user computing device 110. In anexample embodiment, the OCR system 140 is part of the payment processingsystem. In an example embodiment, the OCR system 140 transmits thepayment card information captured from the card image to the digitalwallet application module 119 on the user computing device 110. Examplepayment card information may comprise a user's name (as it appears onthe payment card 130), a financial account number extracted from thepayment card 130, an expiration date associated with the payment card130, an image of the payment card 130, and any other useful orappropriate information associated with the payment card 130 or theuser's financial account.

Returning to block 360, if the OCR system 140 determines that thepayment card is an open-loop payment card, the method 300 proceeds toblock 370. In an example embodiment, the OCR system 140 determines thatthe payment card is an open-loop payment card 130 based on theidentified visual objects in the payment card image, extracted text fromthe visual card image, regions of color, shape, pattern, lines, shading,or brightness on the payment card 130, and/or other appropriate featuresof the payment card 130 that can be optically detected by the OCR system140. For example, the OCR system 140 may identify a payment card 130 asan open-loop payment card 130 based on the presence of an issuer systemname, acquirer system name, and/or financial institution system name onthe payment card image. For example, the OCR system 140 extracts textfrom the payment card 130 image. In this example, the OCR system 140accesses a database comprising payment card 130 features such as logos,color schemes, and text associated with known payment card 130. In thisexample, the OCR system 140 searches the database for text that matchesthe extracted text and determines that the extracted text matches anissuer system name, acquirer system name, and/or financial institutionsystem name in the database. In this example, the OCR system 140determines the card type as open-loop or closed-loop based on theinformation in the database. For example, the OCR system 140 classifiesa payment card 130 comprising text that matches an issuer system name inthe database as an open-loop payment card. In another example, thedatabase comprises a card type (open-loop or closed-loop) associatedwith the issuer system name, acquirer system name, and/or financialinstitution system name and the OCR system 140 determines classifies thepayment card 130 according to the card type listed in the databaseassociated with the extracted text.

In another example, the OCR system 140 detects a logo of a certaincolor, shape, and shading in a certain position on the payment card 130and searches a database on the OCR system application module 143 for atext description of the logo. In this example embodiment, the OCR system140 may determine that the payment card 130 is a credit card, debitcard, or universal gift card, and thus an open-loop payment card 130.For example, the text description comprises an issuer system orfinancial institution system name. In this example, the OCR system 140determines that the payment card 130 should be classified as open-loopbased on the presence of an issuer system or financial institutionsystem name in the text description of the logo. In an exampleembodiment, the database comprises a payment card 130 type associatedwith the text description of the logo and the OCR system 140 determinesthe payment card 130 classification as open-loop or closed-loop based onthe payment card 130 type associated with the text description.

In block 370, the OCR system 140 determines whether open-loop paymentcards are savable in the digital wallet account. In another exampleembodiment, the OCR system 140 communicates with the payment processingsystem associated with the digital wallet account to determine ifopen-loop cards are savable in the digital wallet account. In certainexample embodiments, the digital wall et account is configured not toaccept open-loop payment cards 130 due to security concerns or due torules agreed upon between the OCR system and an issuer system, merchantsystem, or acquirer system associated with the payment card 130. Forexample, the digital wallet account and associated digital walletapplication 119 may only be configured to accept one-merchant giftcards. In another example embodiment, open-loop payment cards aresavable in the digital wallet account, but the account number and/orother important user financial account information associated with thepayment card 130 must be blurred or obscured if displayed on the usercomputing device 110.

If the OCR system determines that open-loop payment cards are notsavable, the method 300 proceeds to block 380.

In block 380, the user is notified that the payment card is not savableon the digital wallet. For example, the OCR system 140 transmits anotification to the user computing device 110 that the open-loop paymentcard type can not be saved on the digital wallet account. In thisexample, the user computing device 110 displays the notification. Anexample notification may read “We're sorry. Credit/debit cards can notbe saved by this application.” In an example embodiment, the OCR system140 deletes any extracted financial account information extracted fromthe open-loop payment card 130 and any images of the open-loop paymentcard 130. In another example embodiment, the OCR system 140 uses aredacted image of the open-loop payment card 130 to train a computermodel to identify similar open-loop payment cards 130 in the future. Inanother example embodiment, open-loop payment cards 130 are not savablein the digital wallet account or associated digital wallet application119, but are savable in an alternative digital wallet account andassociated digital wallet application 119 resident on the user computingdevice 110 and appropriate for saving open-loop payment cards 130. Inthis example embodiment, the OCR system 140 may transmit the financialaccount information and image of an identified open-loop payment card130 to the alternative digital wallet account. In this exampleembodiment, the OCR system 140 may transmit a request to the usercomputing device 110 alerting the user that the payment card 130 may notbe stored in the digital wallet account and asking user permission tostore the payment card 130 information in an alternative digital walletaccount. In this example embodiment, if the user consents, the paymentinformation is saved by the alternative digital wallet application 119,and if the user does not consent, the financial account information andassociated payment card 130 image are deleted by the OCR system 140 orused for other purposes as previously discussed. In this exampleembodiment, the user may also be given the option to change the settingsof the digital wallet account and associated digital wallet application119 to allow saving of open-loop cards. In this example embodiment, ifthe user changes the digital wallet account settings, the open-looppayment card 130 may be saved in the digital wallet account.

Returning to block 370, if the OCR system 140 determines that open-looppayment cards are savable, the method 300 proceeds to block 390.

In block 390, the OCR system 140 saves payment card information in thedigital wallet account. In an example embodiment, the OCR system 140communicates with the payment processing system associated with thedigital wallet application to save the payment card information in thedigital wallet account on the payment processing system and/or thedigital wallet application on the user computing device 110. In anexample embodiment, the OCR system 140 is part of the payment processingsystem. In an example embodiment, the OCR system 140 transmits thepayment card information to the digital wallet application module 119 onthe user computing device 110. Example payment card information maycomprise a user's name (as it appears on the payment card 130), afinancial account number extracted from the payment card 130, anexpiration date associated with the payment card 130, an image of thepayment card 130, and any other useful or appropriate informationassociated with the payment card 130 or the user's financial account.

In block 395, the user selects a saved payment card and conducts atransaction. The method for selecting a payment card 130 for use in atransaction is described in more detail hereinafter with reference tothe method described in FIG. 5.

FIG. 5 is a block diagram depicting a method 395 to select a paymentcard to use for a digital wallet transaction, in accordance with certainexample embodiments. The method 390 is described with reference to thecomponents illustrated in FIG. 1.

In block 510, the user initiates a transaction. In an exampleembodiment, the user desires to initiate a peer to peer (“P2P”)transaction with another user having a digital wallet account with thepayment processing system. In an example embodiment, the user selectsthe digital wallet application 119 on the user computing device 110. Inthis example embodiment, the user selects an option to initiate aP2Ptransaction using the digital wallet account. In an example, the useractuates one or more objects on the user interface 111 to initiate theP2P transaction. An example P2P transaction comprises a transfer offunds from the user to a payee. In an example embodiment, the userselects a payee for the P2P transaction via the digital walletapplication 119. In other example embodiments, the user initiates adigital wallet transaction with a merchant system. For example, the useraccesses a merchant system website via a web browser on the usercomputing device 110, selects one or more items for purchase, andinitiates a transaction on the merchant system website by actuating anobject on the user interface 111.

In block 520, the digital wallet application 119 presents the user witha list of saved payment cards 130. In an example embodiment, the digitalwallet application 119 is associated with a payment processing systemcomprising a digital wallet account associated with the user. In anexample embodiment, the digital wallet application 119 communicates withthe payment processing system to access financial account informationstored in the digital wallet account. In an example embodiment, thedigital wallet application 119 stores financial account informationassociated with one or more payment cards 150 in the data storage unit115 of the user computing device 110. In the example embodimentsdescribed herein, a payment card 130 may comprise a credit card, a debitcard, a stored value card, a gift card, a coupon, a voucher card, arewards points card, a loyalty card, or other payment card 130appropriate for use in a transaction.

In block 530, the user selects a payment card 130. In an exampleembodiment, the user actuates an object on the user interface 111 toselect the payment card 130 from one or more payment cards stored in theuser's digital wallet account. For example, the user 101 selects a debitcard from the list of payment cards 130. In another example, the user101 selects a credit card from the list of payment cards 130. In anexample embodiment, the payment processing system 150 receivesnotification of the user selection of the payment card and retrievesfinancial account information associated with the payment card selectedby the user for use in the payment transaction. For example, thefinancial account information is stored in the user's digital walletaccount.

In block 540, the transaction is processed. In an example embodiment,the payment processing system associated with the digital wallet accountand the digital wallet application 119 processes a P2P transaction basedon the financial account information associated with the credit paymentcard 130. In an example embodiment, the transaction comprises a transferof funds to or from a user financial account associated with the paymentcard 130. For example, a P2P transaction involves the transfer of fundsbetween the user financial account and a second user financial accountof another user having a digital wallet account associated with thepayment processing system. In another example, the transaction comprisesa transfer of funds between the user financial account associated withthe payment card 130 and a merchant system account. In another exampleembodiment, the payment processing system or a merchant system process atransaction between the user and an online website using the financialaccount information associated with the credit payment card 130.

Other Example Embodiments

FIG. 6 depicts a computing machine 2000 and a module 2050 in accordancewith certain example embodiments. The computing machine 2000 maycorrespond to any of the various computers, servers, mobile devices,embedded systems, or computing systems presented herein. The module 2050may comprise one or more hardware or software elements configured tofacilitate the computing machine 2000 in performing the various methodsand processing functions presented herein. The computing machine 2000may include various internal or attached components such as a processor2010, system bus 2020, system memory 2030, storage media 2040,input/output interface 2060, and a network interface 2070 forcommunicating with a network 2080.

The computing machine 2000 may be implemented as a conventional computersystem, an embedded controller, a laptop, a server, a mobile device, asmartphone, a set-top box, a kiosk, a vehicular information system, onemore processors associated with a television, a customized machine, anyother hardware platform, or any combination or multiplicity thereof. Thecomputing machine 2000 may be a distributed system configured tofunction using multiple computing machines interconnected via a datanetwork or bus system.

The processor 2010 may be configured to execute code or instructions toperform the operations and functionality described herein, managerequest flow and address mappings, and to perform calculations andgenerate commands. The processor 2010 may be configured to monitor andcontrol the operation of the components in the computing machine 2000.The processor 2010 may be a general purpose processor, a processor core,a multiprocessor, a reconfigurable processor, a microcontroller, adigital signal processor (“DSP”), an application specific integratedcircuit (“ASIC”), a graphics processing unit (“GPU”), a fieldprogrammable gate array (“FPGA”), a programmable logic device (“PLD”), acontroller, a state machine, gated logic, discrete hardware components,any other processing unit, or any combination or multiplicity thereof.The processor 2010 may be a single processing unit, multiple processingunits, a single processing core, multiple processing cores, specialpurpose processing cores, co-processors, or any combination thereof.According to certain embodiments, the processor 2010 along with othercomponents of the computing machine 2000 may be a virtualized computingmachine executing within one or more other computing machines.

The system memory 2030 may include non-volatile memories such asread-only memory (“ROM”), programmable read-only memory (“PROM”),erasable programmable read-only memory (“EPROM”), flash memory, or anyother device capable of storing program instructions or data with orwithout applied power. The system memory 2030 may also include volatilememories such as random access memory (“RAM”), static random accessmemory (“SRAM”), dynamic random access memory (“DRAM”), and synchronousdynamic random access memory (“SDRAM”). Other types of RAM also may beused to implement the system memory 2030. The system memory 2030 may beimplemented using a single memory module or multiple memory modules.While the system memory 2030 is depicted as being part of the computingmachine 2000, one skilled in the art will recognize that the systemmemory 2030 may be separate from the computing machine 2000 withoutdeparting from the scope of the subject technology. It should also beappreciated that the system memory 2030 may include, or operate inconjunction with, a non-volatile storage device such as the storagemedia 2040.

The storage media 2040 may include a hard disk, a floppy disk, a compactdisc read only memory (“CD-ROM”), a digital versatile disc (“DVD”), aBlu-ray disc, a magnetic tape, a flash memory, other non-volatile memorydevice, a solid state drive (“SSD”), any magnetic storage device, anyoptical storage device, any electrical storage device, any semiconductorstorage device, any physical-based storage device, any other datastorage device, or any combination or multiplicity thereof. The storagemedia 2040 may store one or more operating systems, application programsand program modules such as module 2050, data, or any other information.The storage media 2040 may be part of, or connected to, the computingmachine 2000. The storage media 2040 may also be part of one or moreother computing machines that are in communication with the computingmachine 2000 such as servers, database servers, cloud storage, networkattached storage, and so forth.

The module 2050 may comprise one or more hardware or software elementsconfigured to facilitate the computing machine 2000 with performing thevarious methods and processing functions presented herein. The module2050 may include one or more sequences of instructions stored assoftware or firmware in association with the system memory 2030, thestorage media 2040, or both. The storage media 2040 may thereforerepresent examples of machine or computer readable media on whichinstructions or code may be stored for execution by the processor 2010.Machine or computer readable media may generally refer to any medium ormedia used to provide instructions to the processor 2010. Such machineor computer readable media associated with the module 2050 may comprisea computer software product. It should be appreciated that a computersoftware product comprising the module 2050 may also be associated withone or more processes or methods for delivering the module 2050 to thecomputing machine 2000 via the network 2080, any signal-bearing medium,or any other communication or delivery technology. The module 2050 mayalso comprise hardware circuits or information for configuring hardwarecircuits such as microcode or configuration information for an FPGA orother PLD.

The input/output (“I/O”) interface 2060 may be configured to couple toone or more external devices, to receive data from the one or moreexternal devices, and to send data to the one or more external devices.Such external devices along with the various internal devices may alsobe known as peripheral devices. The I/O interface 2060 may include bothelectrical and physical connections for operably coupling the variousperipheral devices to the computing machine 2000 or the processor 2010.The I/O interface 2060 may be configured to communicate data, addresses,and control signals between the peripheral devices, the computingmachine 2000, or the processor 2010. The I/O interface 2060 may beconfigured to implement any standard interface, such as small computersystem interface (“SCSI”), serial-attached SCSI (“SAS”), fiber channel,peripheral component interconnect (“PCI”), PCI express (PCIe), serialbus, parallel bus, advanced technology attached (“ATA”), serial ATA(“SATA”), universal serial bus (“USB”), Thunderbolt, FireWire, variousvideo buses, and the like. The I/O interface 2060 may be configured toimplement only one interface or bus technology. Alternatively, the I/Ointerface 2060 may be configured to implement multiple interfaces or bustechnologies. The I/O interface 2060 may be configured as part of all ofor to operate in conjunction with, the system bus 2020. The I/Ointerface 2060 may include one or more buffers for bufferingtransmissions between one or more external devices, internal devices,the computing machine 2000, or the processor 2010.

The I/O interface 2060 may couple the computing machine 2000 to variousinput devices including mice, touch-screens, scanners, electronicdigitizers, sensors, receivers, touchpads, trackballs, cameras,microphones, keyboards, any other pointing devices, or any combinationsthereof. The I/O interface 2060 may couple the computing machine 2000 tovarious output devices including video displays, speakers, printers,projectors, tactile feedback devices, automation control, roboticcomponents, actuators, motors, fans, solenoids, valves, pumps,transmitters, signal emitters, lights, and so forth.

The computing machine 2000 may operate in a networked environment usinglogical connections through the network interface 2070 to one or moreother systems or computing machines across the network 2080. The network2080 may include wide area networks (WAN), local area networks (LAN),intranets, the Internet, wireless access networks, wired networks,mobile networks, telephone networks, optical networks, or combinationsthereof. The network 2080 may be packet switched, circuit switched, ofany topology, and may use any communication protocol. Communicationlinks within the network 2080 may involve various digital or an analogcommunication media such as fiber optic cables, free-space optics,waveguides, electrical conductors, wireless links, antennas,radio-frequency communications, and so forth.

The processor 2010 may be connected to the other elements of thecomputing machine 2000 or the various peripherals discussed hereinthrough the system bus 2020. It should be appreciated that the systembus 2020 may be within the processor 2010, outside the processor 2010,or both. According to some embodiments, any of the processor 2010, theother elements of the computing machine 2000, or the various peripheralsdiscussed herein may be integrated into a single device such as a systemon chip (“SOC”), system on package (“SOP”), or ASIC device.

In situations in which the systems discussed here collect personalinformation about users, or may make use of personal information, theusers may be provided with an opportunity or option to control whetherprograms or features collect user information (e.g., information about auser's social network, social actions or activities, profession, auser's preferences, or a user's current location), or to control whetherand/or how to receive content from the content server that may be morerelevant to the user. In addition, certain data may be treated in one ormore ways before it is stored or used, so that personally identifiableinformation is removed. For example, a user's identity may be treated sothat no personally identifiable information can be determined for theuser, or a user's geographic location may be generalized where locationinformation is obtained (such as to a city, ZIP code, or state level),so that a particular location of a user cannot be determined. Thus, theuser may have control over how information is collected about the userand used by a content server.

Embodiments may comprise a computer program that embodies the functionsdescribed and illustrated herein, wherein the computer program isimplemented in a computer system that comprises instructions stored in amachine-readable medium and a processor that executes the instructions.However, it should be apparent that there could be many different waysof implementing embodiments in computer programming, and the embodimentsshould not be construed as limited to any one set of computer programinstructions. Further, a skilled programmer would be able to write sucha computer program to implement an embodiment of the disclosedembodiments based on the appended flow charts and associated descriptionin the application text. Therefore, disclosure of a particular set ofprogram code instructions is not considered necessary for an adequateunderstanding of how to make and use embodiments. Further, those skilledin the art will appreciate that one or more aspects of embodimentsdescribed herein may be performed by hardware, software, or acombination thereof, as may be embodied in one or more computingsystems. Moreover, any reference to an act being performed by a computershould not be construed as being performed by a single computer as morethan one computer may perform the act.

The example embodiments described herein can be used with computerhardware and software that perform the methods and processing functionsdescribed herein. The systems, methods, and procedures described hereincan be embodied in a programmable computer, computer-executablesoftware, or digital circuitry. The software can be stored oncomputer-readable media. For example, computer-readable media caninclude a floppy disk, RAM, ROM, hard disk, removable media, flashmemory, memory stick, optical media, magneto-optical media, CD-ROM, etc.Digital circuitry can include integrated circuits, gate arrays, buildingblock logic, field programmable gate arrays (FPGA), etc.

The example systems, methods, and acts described in the embodimentspresented previously are illustrative, and, in alternative embodiments,certain acts can be performed in a different order, in parallel with oneanother, omitted entirely, and/or combined between different exampleembodiments, and/or certain additional acts can be performed, withoutdeparting from the scope and spirit of various embodiments. Accordingly,such alternative embodiments are included in the scope of the followingclaims, which are to be accorded the broadest interpretation so as toencompass such alternate embodiments.

Although specific embodiments have been described above in detail, thedescription is merely for purposes of illustration. It should beappreciated, therefore, that many aspects described above are notintended as required or essential elements unless explicitly statedotherwise. Modifications of, and equivalent components or actscorresponding to, the disclosed aspects of the example embodiments, inaddition to those described above, can be made by a person of ordinaryskill in the art, having the benefit of the present disclosure, withoutdeparting from the spirit and scope of embodiments defined in thefollowing claims, the scope of which is to be accorded the broadestinterpretation so as to encompass such modifications and equivalentstructures.

1. A computer-implemented method to categorize payment cards,comprising: receiving, by one or more computing devices and from a usercomputing device, an image comprising an image of a payment card;extracting, by the one or more computing devices, one or more textobjects and one or more visual objects from the image of the paymentcard; determining, by the one or more computing devices and based on theone or more extracted text objects and the one or more extracted visualobjects, a categorical designation for the payment card and financialaccount information associated with the payment card; and transmitting,by the one or more computing devices and to the user computing device,the financial account information associated with the payment card andthe categorical designation for the payment card for storage in the usercomputing device based on the categorical designation.
 2. The method ofclaim 1, wherein the categorical designation comprises one of anopen-loop payment card and a closed-loop payment card.
 3. The method ofclaim 2, wherein the user computing device discards the receivedfinancial account information associated with the payment card if thepayment card has a categorical designation comprising an open-looppayment card.
 4. The method of claim 1, wherein the user computingdevice discards the received financial account information based on thecategorical designation.
 5. The method of claim 1, wherein a usercomputing device captures the image of the payment card and transmitsthe image of the payment card to the one or more computing devices. 6.The method of claim 1, wherein a user computing device captures theimage of the payment card via a camera device communicating with theuser computing device via a network and transmits the image of thepayment card to the one or more computing devices.
 7. The method ofclaim 1, wherein the user computing device initiates a transaction usingthe saved financial account information associated with the paymentcard.
 8. The method of claim 1, wherein one or more of the one or moreextracted visual objects comprise a logo associated with an issuersystem, an acquirer system, or a financial institution system.
 9. Acomputer program product, comprising: a non-transitory computer-readablestorage device having computer-readable program instructions embodiedthereon that when executed by a computer cause the computer tocategorize payment cards, the computer-readable instructions comprising:computer-readable program instructions to extract one or more textobjects and one or more visual objects from an image of a payment card;computer-readable program instructions to determine, based on the one ormore extracted text objects and the one or more extracted visualobjects, a categorical designation for the payment card and financialaccount information associated with the payment card; andcomputer-readable program instructions to transmit, to a user computingdevice, the financial account information associated with the paymentcard and the categorical designation for the payment card for storage inthe user computing device based on the categorical designation.
 10. Thecomputer program product of claim 9, wherein the categorical designationcomprises one of an open-loop payment card and a closed-loop paymentcard.
 11. The computer program product of claim 10, wherein the usercomputing device discards the received financial account informationassociated with the payment card if the payment card has a categoricaldesignation comprising an open-loop payment card.
 12. The computerprogram product of claim 9, wherein the user computing device discardsthe received financial account information based on the categoricaldesignation.
 13. The computer program product of claim 9, wherein theuser computing device captures the image of the payment card via acamera device communicating with the user computing device via anetwork.
 14. The computer program product of claim 9, wherein one ormore of the one or more extracted visual objects comprise a logoassociated with an issuer system, an acquirer system, or a financialinstitution system.
 15. A system to categorize payment cards,comprising: a storage device; and a processor communicatively coupled tothe storage device, wherein the processor executes application codeinstructions that are stored in the storage device to cause the systemto: receive, from a user computing device, an image comprising an imageof a payment card captured via the user computing device; extract one ormore text objects and one or more visual objects from the image of thepayment card; determine, based on the one or more extracted text objectsand the one or more extracted visual objects, a categorical designationfor the payment card and financial account information associated withthe payment card; and transmit, to the user computing device, thefinancial account information associated with the payment card and thecategorical designation for the payment card for storage in the usercomputing device based on the categorical designation.
 16. The system ofclaim 15, wherein the categorical designation comprises one of anopen-loop payment card or a closed-loop payment card.
 17. The system ofclaim 15, wherein the user computing device discards the receivedfinancial account information based on the categorical designation. 18.The system of claim 17, wherein the user computing device discards thereceived financial account information associated with the payment cardif the payment card has a categorical designation comprising anopen-loop payment card.
 19. The system of claim 15, wherein the usercomputing device captures the image of the payment card via a cameradevice communicating with the user computing device via a network 20.The system of claim 15, wherein one or more of the one or more extractedvisual objects comprise a logo associated with an issuer system, anacquirer system, or a financial institution system.